Skip to content

Conversation

Bodigrim
Copy link
Collaborator

The lukko package was meant to be a temporary workaround, and relevant improvements have been long accessible from base:GHC.IO.Handle.Lock.

As suggested at haskellari/lukko#39 (comment), let's switch the default value of the lukko flag of cabal-install from True to False. Additionally, to be on the safe side, we make it an automatic one, so that if things suddenly go terribly wrong a Hackage revision could sort it back.

The same change has been implemented for the hackage-security package sometime ago in haskell/hackage-security#322, and there seems to be no complaints.

Template B: This PR (hopefully) does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@Bodigrim Bodigrim linked an issue Jun 18, 2025 that may be closed by this pull request
@Bodigrim Bodigrim force-pushed the make-lukko-flag-automatic-and-false-by-default branch from 97562d7 to 73f8fe5 Compare June 18, 2025 22:27
@Bodigrim Bodigrim marked this pull request as ready for review June 18, 2025 22:36
@Bodigrim Bodigrim added the merge me Tell Mergify Bot to merge label Jun 19, 2025
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days labels Jun 19, 2025
The lukko package (https://hackage.haskell.org/package/lukko)
was meant to be a temporary workaround, and relevant improvements
have been long accessible from base:GHC.IO.Handle.Lock.

As suggested at haskellari/lukko#39 (comment),
let's switch the default value of the lukko flag of cabal-install
from True to False. Additionally, to be on the safe side, we make it
an automatic one, so that if things go terribly wrong a Hackage revision
could sort it back.

The same change has been implemented for the hackage-security package
sometime ago in haskell/hackage-security#322,
and there seems to be no complaints.
@Mikolaj Mikolaj force-pushed the make-lukko-flag-automatic-and-false-by-default branch from 73f8fe5 to 7d9d53e Compare June 21, 2025 00:35
mergify bot added a commit that referenced this pull request Jun 21, 2025
@mergify mergify bot merged commit 413621c into master Jun 21, 2025
55 checks passed
@mergify mergify bot deleted the make-lukko-flag-automatic-and-false-by-default branch June 21, 2025 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flip the default value of lukko flag in hackage-security

3 participants